Repository navigation
module-kit 0.5.0: effect "publish", with destructiveHint and no publication in production until D1 - #11
Merged
Conversation
…cation in production until D1 Decision D1 of LZD-0037 (Matěj, 2026-11-18): agents write drafts on their own and publish only after the person's explicit "Publikuj". A tool's effect is read, prepare, write (a draft) or publish (a publication, a tool of its own). The registry gives a publication destructiveHint itself; a draft and a publication pass the same writer gate; a production application offers no publication until the Owner decides how the App knows the person's "Publikuj" (AGENT_PUBLICATION_IN_PRODUCTION, the one place that changes), a development version does. A 0.4 declaration of a publication (write with publishesData true, publicationConsent) is refused at registration. Readiness can then require 0.5.0 as the minimum version instead of reading the source. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
agentrozjedemeai
approved these changes
Nov 18, 2026
agentrozjedemeai
left a comment
Collaborator
There was a problem hiding this comment.
Approved. The publication gate and annotations match the decision in Lazurio/LazurioPlatform#1078. TypeScript checks and 113 tests passed locally; both TypeScript and Python CI jobs passed.
Non-blocking: LZD-0037 still describes the earlier publicationConsent behavior. Its update is proposed in LazurioDevelopment/mission-control-data#258.
Order and migrations: Keep Clients on 0.4.x until the Owner decides the production publication mechanism; update LZD-0037 via https://github.com/LazurioDevelopment/mission-control-data/pull/258 before coordinating adoption of 0.5.0.
— Pablo
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
module-kit 0.5.0: tools declare a publication as
effect: "publish". The library itself guaranteesdestructiveHintand that a production application offers no publication until decision D1 of LZD-0037 is settled. This is the library side of the Module Standard's "Effects and publication" (Lazurio/LazurioPlatform#1078).Why: Matěj decided D1 on 2026-11-18: agents write drafts on their own and publish only after the person's explicit "Publikuj". Thread A (MODUL A APLIKACE) proposed moving both guarantees into the library, because readiness cannot find publication tools reliably by reading the source (#1079). Readiness then only requires this release as the minimum version.
Change (breaking, hence 0.5.0)
ToolEffect:read,prepare,write(a draft) andpublish(a publication, a tool of its own).destructiveHint: truecomes exactly fromeffect: "publish". The App does not set it.dataWritergate, so neither is offered in a read-only copy./mcpor on the page whiledeployment()isproduction. A call to one is refused withforbiddenand a message naming LZD-0037 D1. A development version offers it.AGENT_PUBLICATION_IN_PRODUCTION = falseis the one place that changes once Matěj decides how the App knows the person's "Publikuj".effect: "write"withpublishesData: true, anypublicationConsent, and an unknown effect. The type refuses them too.Not decided here, flagged for the coordinator: Clients (HumanAndMachine-ai/rozjedemeai-clients#35) uses
publicationConsenttoday. That follows Matěj's DEV-6696 decision that agents publish Clients tickets directly. On 0.5.0 its ticket publication would not be offered in production until D1's variant is decided. Clients therefore stays on 0.4.x until then, unless Matěj decides otherwise.Verification:
bun run check(tsc and Biome) andbun test(113 tests) pass. The new tests cover:/mcpand on the page;destructiveHint: true;effectOfanswerspublish.The README's install line stays at
v0.4.0until this is released.Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:3e1c89fb-5ac2-43b2-9ec4-23f4a2e51382
🤖 Generated with Claude Code